NO-ISSUE: Synchronize From Upstream Repositories #695

openshift-bot · 2024-02-15T00:04:48Z

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date	Commit	Author	Message
2024-02-14 12:47:26	operator-framework/operator-lifecycle-manager@6243cd1	Joe Lanford	add related objects to ClusterOperator for better OpenShift must-gather collection (#3175)
2024-02-16 21:24:10	operator-framework/operator-lifecycle-manager@40ba65c	Jacob Floyd	Apply Subscription.Spec.Config.Annotations to Deployments, Pods, ApiServices (#3169)
2024-02-20 14:19:38	operator-framework/operator-lifecycle-manager@9f42a6f	Mikalai Radchuk	Fixes log line for pod creation (#3178)
2024-02-22 17:35:22	operator-framework/operator-lifecycle-manager@cdf8949	Jordan Keister	change dco policy to enable merge queues (#3179)
2024-02-14 17:42:49	operator-framework/operator-registry@d924b76	Jordan Keister	use contributions path as fallback search for template inputs (#1221)
2024-02-14 18:48:35	operator-framework/operator-registry@27612df	dependabot[bot]	build(deps): bump github.com/opencontainers/image-spec (#1220)
2024-02-21 20:34:29	operator-framework/operator-registry@efddcb3	Jordan Keister	moving codecov to token-based (#1228)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-runtime
/cc @openshift/openshift-team-operator-ecosystem

openshift-ci-robot · 2024-02-15T00:04:52Z

@openshift-bot: This pull request explicitly references no jira issue.

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message

2024-02-14 17:42:49 operator-framework/operator-registry@d924b76 Jordan Keister use contributions path as fallback search for template inputs (#1221)

2024-02-14 18:48:35 operator-framework/operator-registry@27612df dependabot[bot] build(deps): bump github.com/opencontainers/image-spec (#1220)

2024-02-14 12:47:26 operator-framework/operator-lifecycle-manager@6243cd1 Joe Lanford add related objects to ClusterOperator for better OpenShift must-gather collection (#3175)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-runtime
/cc @openshift/openshift-team-operator-ecosystem

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci · 2024-02-15T00:05:07Z

@openshift-bot: GitHub didn't allow me to request PR reviews from the following users: openshift/openshift-team-operator-ecosystem.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message

2024-02-14 17:42:49 operator-framework/operator-registry@d924b76 Jordan Keister use contributions path as fallback search for template inputs (#1221)

2024-02-14 18:48:35 operator-framework/operator-registry@27612df dependabot[bot] build(deps): bump github.com/opencontainers/image-spec (#1220)

2024-02-14 12:47:26 operator-framework/operator-lifecycle-manager@6243cd1 Joe Lanford add related objects to ClusterOperator for better OpenShift must-gather collection (#3175)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-runtime
/cc @openshift/openshift-team-operator-ecosystem

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

openshift-ci · 2024-02-15T00:05:59Z

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-bot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

DOWNSTREAM_OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci · 2024-02-15T00:06:00Z

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-bot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

DOWNSTREAM_OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci-robot · 2024-02-15T01:35:30Z

/retest-required

Remaining retests: 0 against base HEAD 224501f and 2 for PR HEAD ecdf26f in total

perdasilva · 2024-02-15T10:12:47Z

Found the error log. Not sure exactly what the issue is yet...(here's the artifacts link too)

[FAILED] in [It] - /go/src/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/installplan_e2e_test.go:2928 @ 02/15/24 02:11:11.159
collecting the install-plan-e2e-qzzdg namespace artifacts as the 'creation with permissions' test case failed
collecting logs in the /logs/artifacts artifacts directory
unable to determine kubeconfig path so defaulting to the $KUBECONFIG value

   STEP: This operator was installed into a global operator group, so the roles should have been lifted to clusterroles @ 02/15/24 02:01:09.034
  Found unexpected step registry.ResourceKey{Name:"ins76dht.cluster.com", Kind:"CustomResourceDefinition", Namespace:""}, expected registry.ResourceKey{Name:"nginx9vcgk-stable", Kind:"RoleBinding", Namespace:""}: name has prefix: false kinds match false
  Found unexpected step registry.ResourceKey{Name:"ins76dht.cluster.com", Kind:"CustomResourceDefinition", Namespace:""}, expected registry.ResourceKey{Name:"nginx9vcgk-stable", Kind:"ClusterRole", Namespace:""}: name has prefix: false kinds match false
  Found unexpected step registry.ResourceKey{Name:"ins76dht.cluster.com", Kind:"CustomResourceDefinition", Namespace:""}, expected registry.ResourceKey{Name:"nginx9vcgk-stable", Kind:"ClusterRoleBinding", Namespace:""}: name has prefix: false kinds match false
  Found unexpected step registry.ResourceKey{Name:"ins76dht.cluster.com", Kind:"CustomResourceDefinition", Namespace:""}, expected registry.ResourceKey{Name:"nginx-saj5tf4", Kind:"ServiceAccount", Namespace:""}: name has prefix: false kinds match false
  Found unexpected step registry.ResourceKey{Name:"ins76dht.cluster.com", Kind:"CustomResourceDefinition", Namespace:""}, expected registry.ResourceKey{Name:"nginx9vcgk-stable", Kind:"Role", Namespace:""}: name has prefix: false kinds match false
  STEP: This operator was installed into a global operator group, so the roles should have been lifted to clusterroles @ 02/15/24 02:01:09.035
  Found unexpected step registry.ResourceKey{Name:"nginx-saj5tf4", Kind:"ServiceAccount", Namespace:""}, expected registry.ResourceKey{Name:"nginx9vcgk-stable", Kind:"ClusterRoleBinding", Namespace:""}: name has prefix: false kinds match false
  Found unexpected step registry.ResourceKey{Name:"nginx-saj5tf4", Kind:"ServiceAccount", Namespace:""}, expected registry.ResourceKey{Name:"nginx9vcgk-stable", Kind:"Role", Namespace:""}: name has prefix: false kinds match false
  Found unexpected step registry.ResourceKey{Name:"nginx-saj5tf4", Kind:"ServiceAccount", Namespace:""}, expected registry.ResourceKey{Name:"nginx9vcgk-stable", Kind:"RoleBinding", Namespace:""}: name has prefix: false kinds match false
  Found unexpected step registry.ResourceKey{Name:"nginx-saj5tf4", Kind:"ServiceAccount", Namespace:""}, expected registry.ResourceKey{Name:"nginx9vcgk-stable", Kind:"ClusterRole", Namespace:""}: name has prefix: false kinds match false
  STEP: This operator was installed into a global operator group, so the roles should have been lifted to clusterroles @ 02/15/24 02:01:09.037
  Found unexpected step registry.ResourceKey{Name:"nginx9vcgk-stable-nginx--5dTsQM5rcZRJ0yJLI1lvf4RSrEFwZkMwrDEula", Kind:"Role", Namespace:""}, expected registry.ResourceKey{Name:"nginx9vcgk-stable", Kind:"ClusterRoleBinding", Namespace:""}: name has prefix: true kinds match false
  Found unexpected step registry.ResourceKey{Name:"nginx9vcgk-stable-nginx--5dTsQM5rcZRJ0yJLI1lvf4RSrEFwZkMwrDEula", Kind:"Role", Namespace:""}, expected registry.ResourceKey{Name:"nginx9vcgk-stable", Kind:"RoleBinding", Namespace:""}: name has prefix: true kinds match false
  Found unexpected step registry.ResourceKey{Name:"nginx9vcgk-stable-nginx--5dTsQM5rcZRJ0yJLI1lvf4RSrEFwZkMwrDEula", Kind:"Role", Namespace:""}, expected registry.ResourceKey{Name:"nginx9vcgk-stable", Kind:"ClusterRole", Namespace:""}: name has prefix: true kinds match false
  STEP: This operator was installed into a global operator group, so the roles should have been lifted to clusterroles @ 02/15/24 02:01:09.038
  Found unexpected step registry.ResourceKey{Name:"nginx9vcgk-stable-nginx--5dTsQM5rcZRJ0yJLI1lvf4RSrEFwZkMwrDEula", Kind:"RoleBinding", Namespace:""}, expected registry.ResourceKey{Name:"nginx9vcgk-stable", Kind:"ClusterRole", Namespace:""}: name has prefix: true kinds match false
  Found unexpected step registry.ResourceKey{Name:"nginx9vcgk-stable-nginx--5dTsQM5rcZRJ0yJLI1lvf4RSrEFwZkMwrDEula", Kind:"RoleBinding", Namespace:""}, expected registry.ResourceKey{Name:"nginx9vcgk-stable", Kind:"ClusterRoleBinding", Namespace:""}: name has prefix: true kinds match false
  STEP: This operator was installed into a global operator group, so the roles should have been lifted to clusterroles @ 02/15/24 02:01:09.178
  Found unexpected step registry.ResourceKey{Name:"nginx9vcgk-stable-1U2GB6g67eBTyg9Hp6l8pOs7DMUjXFEqVgy1Iq", Kind:"ClusterRole", Namespace:""}, expected registry.ResourceKey{Name:"nginx9vcgk-stable", Kind:"ClusterRoleBinding", Namespace:""}: name has prefix: true kinds match false
  STEP: This operator was installed into a global operator group, so the roles should have been lifted to clusterroles @ 02/15/24 02:01:09.32
  STEP: This operator was installed into a global operator group, so the roles should have been lifted to clusterroles @ 02/15/24 02:01:09.321

openshift-ci-robot · 2024-02-15T23:03:43Z

/retest-required

Remaining retests: 0 against base HEAD 12a2e2f and 1 for PR HEAD ecdf26f in total

openshift-ci · 2024-02-16T00:06:59Z

New changes are detected. LGTM label has been removed.

openshift-ci-robot · 2024-02-17T00:06:39Z

@openshift-bot: This pull request explicitly references no jira issue.

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message

2024-02-14 12:47:26 operator-framework/operator-lifecycle-manager@6243cd1 Joe Lanford add related objects to ClusterOperator for better OpenShift must-gather collection (#3175)

2024-02-16 21:24:10 operator-framework/operator-lifecycle-manager@40ba65c Jacob Floyd Apply Subscription.Spec.Config.Annotations to Deployments, Pods, ApiServices (#3169)

2024-02-14 17:42:49 operator-framework/operator-registry@d924b76 Jordan Keister use contributions path as fallback search for template inputs (#1221)

2024-02-14 18:48:35 operator-framework/operator-registry@27612df dependabot[bot] build(deps): bump github.com/opencontainers/image-spec (#1220)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-runtime
/cc @openshift/openshift-team-operator-ecosystem

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci · 2024-02-17T00:06:40Z

New changes are detected. LGTM label has been removed.

perdasilva · 2024-02-19T09:27:25Z

/retest

openshift-ci · 2024-02-21T00:06:59Z

New changes are detected. LGTM label has been removed.

kevinrizza · 2024-02-21T19:41:05Z

/retest

openshift-ci · 2024-02-22T00:07:59Z

New changes are detected. LGTM label has been removed.

…er collection (#3175) Signed-off-by: Joe Lanford <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 6243cd1727b82ab5d4c73febce4aedcd848ef441

…ervices (#3169) * Apply Subscription.Spec.Config.Annotations to deployments Signed-off-by: Jacob Floyd <[email protected]> * Apply Subscription.Spec.Config.Annotations to Deployment Pods Signed-off-by: Jacob Floyd <[email protected]> * Apply Subscription.Spec.Config.Annotations to ApiServices Signed-off-by: Jacob Floyd <[email protected]> * Refactor and Test InjectAnnotationsIntoDeployment Signed-off-by: Jacob Floyd <[email protected]> --------- Signed-off-by: Jacob Floyd <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 40ba65cac74720a51260ebb647f7a13f923bc0fd

Signed-off-by: Mikalai Radchuk <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 9f42a6f3951b3b9d9064233490d24ecfc201a40e

Signed-off-by: Jordan Keister <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: cdf8949948767305da52fd63bf443b4bb882bcf9

Signed-off-by: Jordan Keister <[email protected]> Upstream-repository: operator-registry Upstream-commit: d924b765b93a279dc7af72c3908d88e936262593

Bumps [github.com/opencontainers/image-spec](https://github.com/opencontainers/image-spec) from 1.1.0-rc5 to 1.1.0-rc6. - [Release notes](https://github.com/opencontainers/image-spec/releases) - [Changelog](https://github.com/opencontainers/image-spec/blob/main/RELEASES.md) - [Commits](opencontainers/image-spec@v1.1.0-rc5...v1.1.0-rc6) Upstream-repository: operator-registry Upstream-commit: 27612df8e019df5885d3047db2186bf3e36fecbf --- updated-dependencies: - dependency-name: github.com/opencontainers/image-spec dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Signed-off-by: Jordan Keister <[email protected]> Upstream-repository: operator-registry Upstream-commit: efddcb3e6fd7e972235223b63c599691a0321e10

openshift-ci · 2024-02-23T03:05:08Z

@openshift-bot: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

openshift-bot · 2024-02-23T05:25:08Z

[ART PR BUILD NOTIFIER]

This PR has been included in build operator-lifecycle-manager-container-v4.16.0-202402230438.p0.gaec0f1d.assembly.stream.el9 for distgit operator-lifecycle-manager.
All builds following this will include this PR.

openshift-bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. labels Feb 15, 2024

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 15, 2024

openshift-ci bot requested a review from a team February 15, 2024 00:04

joelanford mentioned this pull request Feb 15, 2024

Add relatedObjects to the initially created ClusterOperator #690

Closed

openshift-bot force-pushed the synchronize-upstream branch from ecdf26f to 519a12e Compare February 16, 2024 00:06

openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 16, 2024

openshift-bot force-pushed the synchronize-upstream branch from 519a12e to bf877f6 Compare February 17, 2024 00:06

openshift-bot added the lgtm Indicates that a PR is ready to be merged. label Feb 17, 2024

openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 17, 2024

openshift-bot added the lgtm Indicates that a PR is ready to be merged. label Feb 18, 2024

openshift-bot force-pushed the synchronize-upstream branch from bf877f6 to 066043d Compare February 21, 2024 00:06

openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 21, 2024

openshift-bot force-pushed the synchronize-upstream branch from 066043d to b447b09 Compare February 22, 2024 00:07

openshift-bot added the lgtm Indicates that a PR is ready to be merged. label Feb 22, 2024

openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 22, 2024

joelanford and others added 7 commits February 23, 2024 00:02

add related objects to ClusterOperator for better OpenShift must-gath…

b3bff9c

…er collection (#3175) Signed-off-by: Joe Lanford <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 6243cd1727b82ab5d4c73febce4aedcd848ef441

Fixes log line for pod creation (#3178)

6a1be31

Signed-off-by: Mikalai Radchuk <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 9f42a6f3951b3b9d9064233490d24ecfc201a40e

change dco policy to enable merge queues (#3179)

be9c2e5

Signed-off-by: Jordan Keister <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: cdf8949948767305da52fd63bf443b4bb882bcf9

use contributions path as fallback search for template inputs (#1221)

eb4756f

Signed-off-by: Jordan Keister <[email protected]> Upstream-repository: operator-registry Upstream-commit: d924b765b93a279dc7af72c3908d88e936262593

moving codecov to token-based (#1228)

ac771e7

Signed-off-by: Jordan Keister <[email protected]> Upstream-repository: operator-registry Upstream-commit: efddcb3e6fd7e972235223b63c599691a0321e10

openshift-bot force-pushed the synchronize-upstream branch from b447b09 to ac771e7 Compare February 23, 2024 00:08

openshift-bot added the lgtm Indicates that a PR is ready to be merged. label Feb 23, 2024

openshift-merge-bot bot merged commit aec0f1d into openshift:master Feb 23, 2024

NO-ISSUE: Synchronize From Upstream Repositories #695

NO-ISSUE: Synchronize From Upstream Repositories #695

Uh oh!

Conversation

openshift-bot commented Feb 15, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Feb 15, 2024

Uh oh!

openshift-ci bot commented Feb 15, 2024

Uh oh!

openshift-ci bot commented Feb 15, 2024

Uh oh!

openshift-ci bot commented Feb 15, 2024

Uh oh!

openshift-ci-robot commented Feb 15, 2024

Uh oh!

perdasilva commented Feb 15, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Feb 15, 2024

Uh oh!

openshift-ci bot commented Feb 16, 2024

Uh oh!

openshift-ci-robot commented Feb 17, 2024

Uh oh!

openshift-ci bot commented Feb 17, 2024

Uh oh!

perdasilva commented Feb 19, 2024

Uh oh!

openshift-ci bot commented Feb 21, 2024

Uh oh!

kevinrizza commented Feb 21, 2024

Uh oh!

openshift-ci bot commented Feb 22, 2024

Uh oh!

openshift-ci bot commented Feb 23, 2024

Uh oh!

openshift-bot commented Feb 23, 2024

Uh oh!

Uh oh!

openshift-bot commented Feb 15, 2024 •

edited

Loading

perdasilva commented Feb 15, 2024 •

edited

Loading